Connection management method, apparatus, computer device and storage medium

ABSTRACT

Disclosed are a connection management method, and a computer device. The method includes sending, by a first terminal, a request message carrying a first QoS parameter to a second terminal. The request message is used for indicating to perform a connection operation between the first terminal and the second terminal according to the first QoS parameter. The connection between the first terminal and the second terminal includes connection for QoS flow, and the connection operation includes at least one of the following: establishing a connection between the first terminal and the second terminal, modifying the connection between the first terminal and the second terminal, or releasing the connection between the first terminal and the second terminal.

RELATED REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2019/081789, filed on Apr. 8, 2019, which claims priority ofInternational Application No. PCT/CN2019/080191 filed on Mar. 28, 2019,the entire contents of which are incorporated herein by reference

BACKGROUND

The present disclosure relates to the field of communications, and inparticular to a connection management method, apparatus, computer deviceand storage medium.

Device-to-Device communication is a sidelink (SL) transmissiontechnology. Compared to a conventional cellular system in whichcommunication data is received or sent through a base station, D2Dcommunication has higher spectrum efficiency and lower transmissiondelay.

In the 3rd Generation Partnership Project (3GPP), D2D is studied inthree stages, that is, a proximity based service (ProSe), vehicle to X(V2X), and wearable devices (FeD2D). In a ProSe system, 3GPP defines aconnection management mechanism based on a PC5 signaling protocol, whichincludes but is not limited to: connection establishment and release,connection security parameter configuration, connection channel qualitymonitoring, etc. In NR-V2X, due to a need to consider unicast andmulticast services, the concept of connection exists between terminals,and 3GPP is discussing how to design a connection management mechanism,but there is still no specific plan.

SUMMARY

In a first aspect, an embodiment of the present disclosure provides aconnection management method, which includes sending, by a firstterminal, a request message carrying a first QoS parameter to a secondterminal, wherein the request message is used for indicating to performa connection operation between the first terminal and the secondterminal for the first QoS parameter.

In a second aspect, an embodiment of the present disclosure provides aconnection management method, which includes receiving, by a secondterminal, a request message carrying a first QoS parameter sent by afirst terminal, wherein the request message is used for indicating toperform a connection operation between the first terminal and the secondterminal for the first QoS parameter.

In a third aspect, an embodiment of the present disclosure provides aconnection management apparatus, including a processing module and asending module; the processing module is configured to send a requestmessage carrying a first QoS parameter to a second terminal through thesending module; wherein the request message is used for indicating toperform a connection operation between the first terminal and the secondterminal for the first QoS parameter.

In a fourth aspect, an embodiment of the present disclosure provides aconnection management apparatus, including a processing module and areceiving module; the processing module is configured to receive arequest message carrying a first QoS parameter sent by a first terminalthrough the receiving module; wherein the request message is used forindicating to perform a connection operation between the first terminaland the second terminal for the first QoS parameter.

In a fifth aspect, an embodiment of the present disclosure provides acomputer device including a memory and a processor, the memory stores acomputer program, and the processor implements steps of the method ofthe first aspect or the second aspect when executing the computerprogram.

In a sixth aspect, an embodiment of the present disclosure provides acomputer-readable storage medium on which a computer program is stored,and the computer program, when executed by a processor, implements stepsof the method of the first aspect or the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an application scenario of a connectionmanagement method provided by an embodiment of the present disclosure;

FIG. 2 is a flowchart of a connection management method provided by anembodiment of the present disclosure;

FIG. 3 is a flowchart of a connection management method provided byanother embodiment of the present disclosure;

FIG. 4 is a flowchart of a connection management method provided bystill another embodiment of the present disclosure;

FIG. 5 is a flowchart of a single connection management process providedby an embodiment of the present disclosure;

FIG. 6 is a flowchart of a dual connection management process providedby an embodiment of the present disclosure

FIG. 7 is a block diagram of a connection management apparatus providedby an embodiment of the present disclosure;

FIG. 8 is a block diagram of a connection management apparatus providedby another embodiment of the present disclosure;

FIG. 9 is a block diagram of a connection management apparatus providedby an embodiment of the present disclosure;

FIG. 10 is a block diagram of a connection management apparatus providedby another embodiment of the present disclosure;

FIG. 11 is a block diagram of a computer device provided by anembodiment of the present disclosure.

DETAILED DESCRIPTION

In order to make objects, technical solutions, and advantages of thepresent disclosure more clear, the present disclosure will be describedin further detail below with reference to drawings and implementations.It should be understood that implementations described herein are onlyfor the purpose of explaining the present disclosure and are notintended to limit the present disclosure.

FIG. 1 is a schematic diagram of an application scenario of a connectionmanagement method provided by an embodiment of the present disclosure,and the scenario may be applied to a vehicle to X system. As shown inFIG. 1, this scenario includes an access network device 1, an accessnetwork device 2, a terminal 3 connected to the access network device 1,and a terminal 4 connected to the access network device 2. Acommunication between the terminal 3 and the terminal 4 is by means ofsidelink communication, and a communication between the terminal and theaccess network device is by means of uplink/downlink communication. Theaccess network device may be a base station, and the terminal may be avehicle-mounted terminal.

Hereinafter, the technical solution of the present disclosure and howthe technical solution of the present disclosure solves theabove-mentioned technical problem will be described in detail throughthe embodiments and the accompanying drawings. The following specificembodiments may be combined with each other, and the same or similarconcepts or processes may not be repeated in some embodiments. It shouldbe noted that, in the connection management method provided by theembodiments of the present disclosure, different execution subjects areused to describe the corresponding embodiments.

FIG. 2 is a flowchart of a connection management method provided by anembodiment of the present disclosure. The method is performed by a firstterminal, which may be the terminal 3 or the terminal 4 in FIG. 1. Thismethod involves a process in which one terminal sends a request messageto another terminal to request operations on the connection between thetwo terminals. As shown in FIG. 1, the method includes the followingsteps.

In S101, the first terminal sends a request message carrying a first QoSparameter to a second terminal, and the request message is used forindicating to perform a connection operation between the first terminaland the second terminal for the first QoS parameter.

The first QoS parameter is used for indicating the first terminal torequest to perform the connection operation between the first terminaland the second terminal for a specific QoS attribute. The first QoSparameter may be a parameter obtained by the first terminal from a localstorage, or may also be a parameter pre-allocated by a network device tothe first terminal, or may also be a parameter obtained by the firstterminal from the network device in real time. Optionally, the first QoSparameter includes but is not limited to at least one of the followinginformation: a PC5 5G quality of service indicator (PQI), V2X 5G qualityof service indicator (VQI), quality of service flow identifier (QFI), adata rate requirement, a communication range requirement, acorrespondence between PQI, VQI, QFI, the data rate requirement, thecommunication range requirement and a radio bearer, a provider serviceidentifier (PSID), and an intelligent transportation systems applicationidentifier (ITS-AID). Optionally, the connection operation between thefirst terminal and the second terminal may include establishing aconnection between the first terminal and the second terminal, modifyingthe connection between the first terminal and the second terminal, orreleasing the connection between the first terminal and the secondterminal. Optionally, the connection operation between the firstterminal and the second terminal may also include switching theconnection between the first terminal and the second terminal, changinga connection mode between the first terminal and the second terminal,and suspending the connection between the first terminal and the secondterminal, etc., which is not limited by the present disclosure.

In this embodiment, when the first terminal needs to perform theconnection operation between the first terminal and the second terminalfor the first QoS parameter, the first terminal generates the requestmessage carrying the first QoS parameter, and sends the request messageto the second terminal. It may be that the network device instructs thefirst terminal to perform the connection operation between the firstterminal and the second terminal for the first QoS parameter, or it maybe that the first terminal initiates to perform the connection operationbetween the first terminal and the second terminal for the first QoSparameter according to a service type, a service status, or an existingconnection condition.

In the connection management method provided by embodiments of thepresent disclosure, the first terminal sends the request messagecarrying the first QoS parameter to the second terminal, since therequest message is used for indicating to perform the connectionoperation between the first terminal and the second terminal for thefirst QoS parameter, signaling interaction may be used for realizing theconnection operation between terminals for a specific QoS parameter. AQoS management mechanism is designed for a QoS flow so as to solve thetechnical problem that a connection management between terminals in aNR-V2X system cannot be realized.

Optionally, in some embodiments, the first QoS parameter may not includethe correspondence between PQI, VQI, QFI, the data rate requirement, thecommunication range requirement and the radio bearer. That is, the firstQoS parameter may include at least one of the following information:PQI, VQI, QFI, the data rate requirement, the communication rangerequirement, PSID, and ITS-AID.

Further, the first terminal may separately send the correspondencebetween PQI, VQI, QFI, the data rate requirement, the communicationrange requirement and the radio bearer to the second terminal. Onepossible implementation includes the first terminal sends firstparameter information to the second terminal; and the parameterinformation includes the correspondence between PQI, VQI, QFI, the datarate requirement, the communication range requirement and the radiobearer. Optionally, the first parameter information is carried in aradio resource control (RRC) signaling sent to the second terminal.Optionally, the request message is carried in the RRC signalingincluding the first parameter information. In this embodiment, the firstterminal may make the first parameter information containing thecorrespondence between PQI, VQI, QFI, the data rate requirement, thecommunication range requirement and the radio bearer to be carried inthe RRC signaling, and send it to the second terminal along with therequest message.

FIG. 3 is a flowchart of a connection management method provided byanother embodiment of the present disclosure. This embodiment involves aspecific implementation process in which the second terminal responds tothe request message of the first terminal. As shown in FIG. 3, themethod includes the following steps.

In S201, the first terminal sends a request message carrying a first QoSparameter to a second terminal, and the request message is used forindicating to perform a connection operation between the first terminaland the second terminal for the first QoS parameter.

For the implementation principle and process description of thisembodiment, refer to S101 of the embodiment in FIG. 2, and details arenot described herein again.

In S202, the first terminal receives a response message sent by thesecond terminal; and the response message is used for indicating whetherthe connection operation is successful.

In this embodiment, when the second terminal receives the requestmessage carrying the first QoS parameter sent by the first terminal, itdetermines whether the second terminal may perform the connectionoperation with the first terminal according to the first QoS parameter,and carries a result in the response message for feeding back to thefirst terminal. The result may be that the second terminal agrees toperform the connection operation between the first terminal and thesecond terminal for the first QoS parameter, and the response messageindicates that the connection operation is successful. For example, thesecond terminal can perform the connection operation between the firstterminal and the second terminal for part or all of the QoS parametersin the first QoS parameters, and then the connection operation succeeds.Alternatively, the result may also be that the second terminal does notagree to perform the connection operation between the first terminal andthe second terminal for the first QoS parameter, and the responsemessage indicates that the connection operation failed. For example, thesecond terminal cannot perform the connection operation between thefirst terminal and the second terminal for all of the QoS parameters inthe first QoS parameters, and the connection operation fails.

Optionally, when the response message indicates that the connectionoperation is successful, the response message may include part or all ofthe QoS parameters that the second terminal is capable of receiving; or,when the response message indicates that the connection operation issuccessful, and the second terminal is capable of receiving all theparameters in the first QoS parameters, the response message may notinclude the QoS parameters, and only indicates the connection operationis successful. Optionally, when the response message indicates theconnection operation fails, the response message may not include the QoSparameters, and only indicates the connection operation fails.

In some embodiments, when the second terminal replies the responsemessage to the first terminal, the response message includes a secondQoS parameter. Optionally, the second QoS parameter is a QoS parameteracceptable to the second terminal. Optionally, the second QoS parameteris a subset of the first QoS parameters.

Further, the second QoS parameter includes at least one of the followinginformation: PQI, VQI, QFI, the data rate requirement, the communicationrange requirement, the correspondence between PQI, VQI, QFI, the datarate requirement, the communication range requirement and the radiobearer, PSID, and ITS-AID.

Optionally, in some embodiments, the second QoS parameters may notinclude the correspondence between PQI, VQI, QFI, the data raterequirement, the communication range requirement and the radio bearer.That is, the second QoS parameter may include at least one of thefollowing information: PQI, VQI, QFI, the data rate requirement, thecommunication range requirement, PSID, and ITS-AID.

Exemplarily, the second terminal may separately send the correspondencebetween PQI, VQI, QFI, the data rate requirement, the communicationrange requirement and the radio bearer to the first terminal. Onepossible implementation includes the first terminal receives secondparameter information sent by the second terminal, and the secondparameter information includes the correspondence between PQI, VQI, QFI,the data rate requirement, the communication range requirement and theradio bearer. Optionally, the second parameter information is carried inthe RRC signaling sent to the first terminal. Optionally, the responsemessage is carried in the RRC signaling including the second parameterinformation. In this embodiment, the second terminal may make the secondparameter information containing the correspondence between PQI, VQI,QFI, the data rate requirement, the communication range requirement andthe radio bearer to be carried in the RRC signaling, and send it to thefirst terminal along with the request message.

In this embodiment, when the second terminal accepts the foregoingconnection operation, the response message may carry QoS parametersacceptable to the second terminal. For example, the first QoS parameterscarried in the request message sent by the first terminal includemapping relationships of PQI, QFI, the communication range requirementand the radio bearer and PSID, and the QoS parameters of the secondterminal include mapping relationships of PQI, the communication rangerequirement and the radio bearer, PSID and ITS-AID, and then the secondQoS parameters acceptable to the second terminal for the first QoSparameters may include the mapping relationships of PQI, thecommunication range requirement and the radio bearer, and PSID.

In the connection management method provided in this embodiment, thefirst terminal sends the request message carrying the first QoSparameter to the second terminal, and the second terminal replies to thefirst terminal with a response message. Since the request message isused for indicating to perform the connection operation between thefirst terminal and the second terminal for the first QoS parameter, andthe second terminal responds to the request message, the connectionmanagement method is further improved. Signaling interaction may be usedfor realizing the connection operation between terminals for a specificQoS parameter. A QoS management mechanism is designed for a QoS flow soas to solve the technical problem that a connection management betweenterminals in a NR-V2X system cannot be realized.

Different connection operations correspond to different requestmessages. Hereinafter, three methods, that is, methods A, B, and C, areused for introducing methods for indicating various connectionoperations through the request message

Method A: the connection operation includes the establishing theconnection between the first terminal and the second terminal, and therequest message includes the first QoS parameter corresponding to theconnection between the first terminal and the second terminal to beestablished.

In this embodiment, when the first terminal establishes the connectionbetween the first terminal and the second terminal for some QoSparameters, the QoS parameters required for the connection between thefirst terminal and the second terminal to be established may be added tothe request message. For example, the first terminal needs to establishthe connection between the first terminal and the second terminal forthe QoS attributes such as PQI, the data rate requirement, thecommunication range requirement, and the radio bearer of PQI, and thefirst terminal adds PQI, the data rate requirement, the communicationrange requirement, and the radio bearer of PQI as the first QoSparameters to the request message such as to send to the secondterminal. In addition, an operation type field may be added to therequest message, and the operation type field may be set as anestablishment identifier.

Method B: the connection operation includes the modifying the connectionbetween the first terminal and the second terminal, and the requestmessage includes the first QoS parameter corresponding to the connectionbetween the first terminal and the second terminal to be modified.

In this embodiment, the connection between the first terminal and thesecond terminal may also be modified. For example, when the firstterminal detects that a performance of a current connection cannot meeta service requirement, the connection may be modified, and the firstterminal may specify the QoS attribute that need to be modified in therequest message. For example, the first terminal wants to modify theconnection between the first terminal and the second terminal for thethree parameters of PQI, the data rate requirement, and thecommunication range requirement, and the first terminal adds PQI, thedata rate requirement, and the communication range requirement as thefirst QoS parameters to the request message such as to send to thesecond terminal. The operation type field is set as a modificationidentifier.

Method C: the connection operation includes the releasing the connectionbetween the first terminal and the second terminal, and the requestmessage includes the first QoS parameter corresponding to the connectionbetween the first terminal and the second terminal to be released.

In this embodiment, when the connection between the first terminal andthe second terminal is idle and there is no service demand for a longtime, the connection may be released to save resources. For example, thefirst terminal wants to release the connection between the terminal andthe second terminal for the three parameters of PQI, the data raterequirement, and the communication range requirement, and the firstterminal adds PQI, the data rate requirement, and the communicationrange requirement as the first QoS parameters to the request messagesuch as to send to the second terminal. The operation type field is setas a release identifier. Optionally, the connection operation includesreleasing the connection between the first terminal and the secondterminal, and the request message may also include an ID of theconnection between the first terminal and the second terminal to bereleased, thereby directly indicating which connection to be released.

In the above embodiment, different request messages are set fordifferent connection operations, and different connection operations maybe quickly realized by changing the QoS parameters in the requestmessage and the operation type indication of the request message. Themethod is flexible and changeable, the method is simple, and may beflexibly applied to various scenarios.

In the above embodiment, there may be multiple connections between thefirst terminal and the second terminal, and different connectionscorrespond to different parameters. Optionally, the connection betweenthe first terminal and the second terminal is a connection for at leastone of the following information a QoS flow, PSID, ITS-AID, PQI, VQI,QFI, the data rate requirement, the communication range requirement, andan application layer ID. That is, the connection between the firstterminal and the second terminal may be a connection for any aboveinformation, or may be a connection for multiple pieces of information.Different parameters may be flexibly selected to establish theconnection between the first terminal and the second terminal accordingto the service requirement, which is not limited by the presentdisclosure. Establishing the connection between the terminals in thismanner may flexibly adapt to multiple scenarios, meet various servicerequirements, and may also avoid the waste of resources or insufficientresources caused by the fixed connection between the terminals.

In the above-mentioned embodiment, there may be multiple connectionsbetween the first terminal and the second terminal at the same time.When there is a need to perform the operations on a connection betweenthe terminals, the first terminal and the second terminal must be clearabout on which connection the operation is performed. Therefore, therequest message and/or the response message include a connectionidentification (ID), and the connection ID is used for distinguishingdifferent connections between the first terminal and the secondterminal, so as to ensure the accuracy of QoS connection management.Optionally, the request message and the response message may alsoinclude information related to the connection ID, which is used forindicating the ID of the connection to be operated.

Optionally, at least one of the following information corresponding tothe different connections between the first terminal and the secondterminal is different: an Internet protocol (IP) address, theapplication layer ID, PSID, ITS-AID, PQI, VQI, L2ID, the data raterequirement, the communication range requirement. That is to say, if thetwo connections between the first terminal and the second terminal haveone different piece of the above information, the two connections arealso different.

In some embodiments, multiple connections need to be established betweenthe first terminal and the second terminal. In order to avoid theestablishment of repeated connections, the following six methods may beadopted.

A first method: the request message includes an application layer IDand/or L2ID used by the first terminal, and the application layer IDused by the first terminal is different from an application layer IDused by a current connection, and the L2ID used by the first terminal isdifferent from L2ID used by the current connection.

In this embodiment, the first terminal may directly add the applicationlayer ID and/or L2ID used by the first terminal to the request message,and the application layer ID and L2ID used by the first terminal aredifferent from the application layer ID and L2ID used by the currentconnection. For example, user A has registered two social accounts A1and A2 at the same time, and the social accounts A1 and A2 are both usedto process the same service, user A and user B have established aconnection for the social account A1, but the user B is not aware thatthe user A further has the social account A2. Then the user A may addthe social account A2 to the request message when sending the requestmessage to a terminal of the user B through the terminal, therebyavoiding establishing the same connection between the terminal of theuser A and the terminal of the user B for the social account A2, andavoiding waste of resources.

A second method: the first terminal sends a first connection updaterequest message to the second terminal; and the first connection updaterequest message includes an application layer ID and/or L2ID used by thefirst terminal, the application layer ID used by the first terminal isdifferent from an application layer ID used by a current connection, andthe L2ID used by the first terminal is different from L2ID used by thecurrent connection.

In this embodiment, the first terminal may also separately send thefirst connection update request message to the second terminal, andinform the second terminal of the application layer ID and/or L2ID usedby the first terminal. Taking user A and user B in the first method asan example, the terminal of the user A may send the first connectionupdate request message carrying the social account A2 to the terminal ofthe user B.

A third method: the response message includes an application layer IDand/or L2ID used by the second terminal, and the application layer IDused by the second terminal is different from an application layer IDused by a current connection, and the L2ID used by the second terminalis different from L2ID used by the current connection.

In this embodiment, similar to the first method, the second terminal mayalso carry the application layer ID and/or L2ID used by the secondterminal in the response message, and the application layer ID and L2IDused by the second terminal are different from the application layer IDand L2ID used by the current connection. For example, the user A hasregistered a social account A1, and the user B has registered socialaccounts B1 and B2, and the social accounts B1 and B2 are both used toprocess the same service, user A and user B have established aconnection for the social accounts A1 and B1, but the user A is notaware that the user B further has the social account B2. Then the user Bmay add the social account B2 to the response message when sending theresponse message to a terminal of the user A1 through the terminal,thereby avoiding establishing the same connection between the terminalof the user A and the terminal of the user B for the social account B2,and avoiding waste of resources.

A fourth method: the first terminal receives a second connection updaterequest message sent by the second terminal; and the second connectionupdate request message includes an application layer ID and/or L2ID usedby the second terminal, and the application layer ID used by the secondterminal is different from an application layer ID used by a currentconnection, and the L2ID used by the second terminal is different fromL2ID used by the current connection.

In this embodiment, the second terminal may also separately send thefirst connection update request message to the first terminal, andinform the first terminal of the application layer ID and/or L2ID usedby the second terminal. Taking user A and user B in the first method asan example, the terminal of the user B may send the second connectionupdate request message carrying the social account B2 to the terminal ofthe user A.

A fifth method: the first terminal sends a first access layer message tothe second terminal; and the first access layer message includes anapplication layer ID and/or L2ID used by the first terminal, theapplication layer ID used by the first terminal is different from anapplication layer ID used by a current connection, and the L2ID used bythe first terminal is different from L2ID used by the currentconnection.

A sixth method: the first terminal receives a second access layermessage sent by the second terminal; and the second access layer messageincludes an application layer ID and/or L2ID used by the secondterminal, and the application layer ID used by the second terminal isdifferent from an application layer ID used by a current connection, andthe L2ID used by the second terminal is different from L2ID used by thecurrent connection.

In the embodiments of the above-mentioned fifth or sixth methods, theapplication layer ID and/or L2ID used by the first terminal or thesecond terminal may also be carried in the access layer message fortransmission. For example, the first terminal carries the applicationlayer ID and/or L2ID used by the first terminal in the first accesslayer message such as to send to the second terminal. The secondterminal carries the application layer ID and/or L2ID used by the secondterminal in the second access layer such as to send to the firstterminal.

In the above-mentioned embodiments, the first terminal and the secondterminal inform each other of the application layer ID and/or L2ID thatare used differently from the current connection in a variety of ways,so as to avoid establishing completely the same connection between thefirst terminal and the second terminal, thereby avoiding the waste ofresources.

In some scenarios, in the process of request message transmission, aphysical ID of the terminal may also be carried in an implicit manner.Optionally, the request message is transmitted based on the L2ID of thetransmission layer, and the L2ID and the L2ID used by other sendingterminals satisfy a preset mapping relationship. Optionally, the mappingrelationship is a mapping relationship defined for the first terminal.Optionally, the mapping relationship is a mapping relationship definedfor the connection between the first terminal and the second terminal.

In this embodiment, the second terminal can infer whether the L2IDphysically belongs to the ID of the same terminal according to themapping relationship. For example, the second terminal can infer whetherit physically belongs to the ID of the same terminal through differentL2IDs. For example, for L2ID-1 and L2ID-2, the same result may beobtained by using the same function f( ) which means that L2ID-1 andL2ID-2 are IDs belonging to the same terminal; or by using differentfunctions f1( ) and f2( ) the same result may be obtained, which meansthat L2ID-1 and L2ID-2 are IDs belonging to the same terminal. The abovefunctions f/f1/f2 may be a function shared by different terminals,different first terminals may use different functions, or differentfunctions are used for different connections between the first terminaland the second terminal.

Optionally, the request message is transmitted based on the L2ID of eachtransmission layer, and L2IDs are in one-to-one correspondence withdifferent PSIDs and/or application layer IDs of the first terminal.Optionally, if any PSID and/or application layer ID of the firstterminal changes, the L2ID changes.

It may be seen from the above embodiments that multiple connections maybe established between two terminals at the same time. For example, aconnection C has been established between the first terminal and thesecond terminal, but due to various reasons such as the service type,the network requirement, and connection quality. It is also necessary toestablish a new connection between the first terminal and the secondterminal. Optionally, the first terminal sends a request message forindicating to establish a new connection in at least one of thefollowing situations: an IP address of an existing connection is notavailable for a new connection; an application layer ID of the existingconnection is not available for the new connection; PSID of the existingconnection is not available for the new connection; PQI of the existingconnection is not available for the new connection; VQI of the existingconnection is not available for the new connection; a data raterequirement of the existing connection is not available for the newconnection; a communication range requirement of the existing connectionis not available for the new connection; a radio bearer of the existingconnection is not available for the new connection; and L2ID of theexisting connection is not available for the new connection.

In this embodiment, when the first terminal determines that at least oneof the IP address, the application layer ID, PSID, PQI, VQI, the datarate requirement, the communication range requirement, the radio bearer,and L2ID of the existing connection is not available for the newconnection, the first terminal sends the request message for indicatingto establish the new connection to the second terminal. The requestmessage includes the QoS parameter corresponding to the new connection.Optionally, the request message for indicating to establish the newconnection is carried in a PC5-S signaling or a PC5-RRC signaling. Thatis to say, the establishment of the new connection may be done throughPC5-S signaling, or the establishment of the new connection may be donethrough PC5-RRC by access layer connection management.

According to the foregoing embodiments, after the first terminaltriggers the establishment of the new connection, the established newconnection includes at least one of the following information: an IPaddress of the new connection is different from an IP address of anexisting connection; an application layer ID of the new connection isdifferent from an application layer ID of the existing connection; PSIDof the new connection is different from PSID of the existing connection;PQI, VQI, a data rate requirement, and a communication range requirementof the new connection are all different from PQI, VQI, a data raterequirement, and a communication range requirement of the existingconnection; a radio bearer of the new connection is different from aradio bearer of the existing connection; and L2ID of the new connectionis different from L2ID of the existing connection.

Further, the following explains the IP of the existing connection, theapplication layer ID of the existing connection, and the L2ID of theexisting connection in the above embodiments respectively, where the IPaddress of the existing connection is an IP address of the firstterminal and/or the second terminal; the IP address of the existingconnection is an IP address of the first terminal and/or the secondterminal in the existing connection; the application layer ID of theexisting connection is an application layer ID of the first terminaland/or the second terminal; the application layer ID of the existingconnection is an application layer ID of the first terminal and/or thesecond terminal in the existing connection; the L2ID of the existingconnection is L2ID of the first terminal and/or the second terminal; andthe L2ID of the existing connection is L2ID of the first terminal and/orthe second terminal in the existing connection.

In the above-mentioned embodiment, when the existing connection cannotsatisfy the QoS, the request message for sending the new connection maybe sent again while the existing connection exists, so as to meet theservice requirement and improve the QoS.

In some scenarios, the network indicates a specific implementationprocess of the connection operation between the first terminal and thesecond terminal through configuration information. Optionally, in theembodiment shown in FIG. 2, before S101 “the sending, by the firstterminal, the request message carrying the first QoS parameter to asecond terminal”, the method may further include receiving, by the firstterminal, configuration information sent by an access network device;and the configuration information is used for indicating whether toperform the connection operation between the first terminal and thesecond terminal for the first QoS parameter. Optionally, in theembodiment shown in FIG. 3, after S202 “the receiving, by the firstterminal, the response message sent by the second terminal”, the methodmay further include receiving, by the first terminal, configurationinformation sent by an access network device; and the configurationinformation is used for indicating whether to perform the connectionoperation between the first terminal and the second terminal for thefirst QoS parameter.

In this embodiment, the access network device may send the configurationinformation to the first terminal to indicate whether to perform theconnection operation between the first terminal and the second terminalfor the first QoS parameter. Optionally, the configuration informationmay include the first QoS parameter, or the configuration informationmay be specifically used for indicating a physical layer parameter forthe first QoS parameter. Optionally, the physical layer parameter of thefirst QoS parameter may include at least one of the followinginformation: a modulation and coding scheme (MCS), a hybrid automaticrepeat request (HARQ), transmission power, a size of an availabletime-frequency resource, etc. Optionally, the configuration informationis carried in a system message or the RRC signaling sent to the firstterminal.

Optionally, different types of core network devices correspond todifferent configuration information. For example, for a 4G core network(EPC), the configuration information includes at least one of thefollowing information: PQI, VQI, the data rate requirement, thecommunication range requirement; for a 5G core network (5GC), theconfiguration information includes QFI. In this embodiment, only EPC and5GC are taken as examples to illustrate that the configurationinformation corresponding to different types of core network devices isdifferent, and it is not limited thereto.

Further, before the first terminal receives the configurationinformation sent by the access network device, the method may furtherinclude reporting, by the first terminal, a third QoS parameter to theaccess network device. Optionally, the third QoS parameter includes atleast one of the following information: PQI, VQI, QFI, a data raterequirement, a communication range requirement, a correspondence betweenPQI, VQI, QFI, the data rate requirement, the communication rangerequirement and a radio bearer, PSID, and ITS-AID. The correspondencebetween PQI, VQI, QFI, the data rate requirement, the communicationrange requirement and the radio bearer may include a correspondence sentby the second terminal for configuring a correspondence used by thefirst terminal. Optionally, third QoS parameters corresponding todifferent types of core network devices are different.

In this embodiment, the first terminal may report the third QoSparameter of the connection between the terminals that needs to beestablished/modified/released to the access network device. The thirdQoS parameter includes at least one of the following but is not limitedto: PQI, VQI, QFI, a data rate requirement, a communication rangerequirement, a correspondence between QFI, PQI, VQI, QFI, the data raterequirement, the communication range requirement and the radio bearer(bearer mapping), PSID, and ITS-AID, etc. For example, to distinguishthe network based on EPC or 5GC, the first terminal reports differentthird QoS parameters, respectively. For EPC, the third QoS parametersinclude at least one of the following: PQI, VQI, the data raterequirement, the communication range requirement-bearer mapping; for5GC, the third QoS parameter includes at least one of the following,QFI, QFI-bearer mapping. The access network device sends the determinedQoS parameters that the first terminal can support to the first terminalthrough the configuration information.

Optionally, the first terminal reports a channel quality parameter ofthe connection from the first terminal to the second terminal to theaccess network device; the channel quality information includes at leastone of a channel busy rate, RSRP, RSRQ, SINR, and RSSI. Differentchannel quality parameters correspond to different configurationinformation. Optionally, the configuration information is specificallyused for determining whether to perform the connection operation betweenthe first terminal and the second terminal for the first QoS parameteraccording to the channel quality information.

In the above embodiments, the terminal may report the third QoSparameter of the connection between the terminals that needs to beestablished/modified/released to the access network device, and may alsoreport the channel quality parameter of the connection from the firstterminal to the second terminal, so that the access network device candetermine the configuration information that satisfies the QoS flowcharacteristics according to the third QoS parameter and the channelquality parameter and send it to the terminal, so that the terminal candetermine the accurate first QoS parameter according to theconfiguration information, thereby effectively establishing, modifyingor releasing the connection between the first terminal and the secondterminal, and improving the reliability of the connection between theterminals.

FIG. 4 is a flowchart of a connection management method provided byanother embodiment of the present disclosure. The execution subject ofthis method is the second terminal, and the second terminal may be theterminal 3 or the terminal 4 in FIG. 1. This method involves a processin which the terminal receives the request message sent by anotherterminal to perform operation on the connection between the twoterminals As shown in FIG. 4, the method includes the following steps.

In S401, the second terminal receives a request message carrying a firstQoS parameter sent by a first terminal, and the request message is usedfor indicating to perform a connection operation between the firstterminal and the second terminal for the first QoS parameter.

For the implementation principles and beneficial effects of theembodiments of the present disclosure, reference may be made to theimplementation principles and beneficial effects of the embodiment shownin FIG. 2, which will not be repeated here.

In one of the embodiments, the method further includes sending, by thesecond terminal, a response message to the first terminal; and theresponse message is used for indicating whether the connection operationis successful. Optionally, the response message includes a second QoSparameter; the second QoS parameter is a QoS parameter acceptable to thesecond terminal. Optionally, the second QoS parameter is a subset of thefirst QoS parameters.

In one of the embodiments, the connection operation includes at leastone of the following: establishing a connection between the firstterminal and the second terminal, modifying the connection between thefirst terminal and the second terminal, and releasing the connectionbetween the first terminal and the second terminal.

In one of the embodiments, the connection operation includes theestablishing the connection between the first terminal and the secondterminal, and the request message includes the first QoS parametercorresponding to the connection between the first terminal and thesecond terminal to be established.

In one of the embodiments, the connection operation includes themodifying the connection between the first terminal and the secondterminal, and the request message includes the first QoS parametercorresponding to the connection between the first terminal and thesecond terminal to be modified.

In one of the embodiments, the connection operation includes themodifying the connection between the first terminal and the secondterminal, and the request message includes the first QoS parametercorresponding to the connection between the first terminal and thesecond terminal to be released.

In one of the embodiments, the first QoS parameter includes at least oneof the following information: PQI, VQI, QFI, a data rate requirement, acommunication range requirement, a correspondence between PQI, VQI, QFI,the data rate requirement, the communication range requirement and aradio bearer, PSID, and ITS-AID.

In one of the embodiments, the first QoS parameter includes at least oneof the following information: PQI, VQI, QFI, a data rate requirement, acommunication range requirement, PSID, and ITS-AID.

In one of the embodiments, the method further includes receiving, by thesecond terminal, first parameter information sent by the first terminal;and the first parameter information includes a correspondence betweenPQI, VQI, QFI, a data rate requirement, a communication rangerequirement and a radio bearer.

In one of the embodiments, the first parameter information is carried ina RRC signaling sent to the second terminal.

In one of the embodiments, the request message is carried in the RRCsignaling including the first parameter information.

In one of the embodiments, the response message includes the second QoSparameter.

In one of the embodiments, the second QoS parameter is the QoS parameteracceptable to the second terminal.

In one of the embodiments, the second QoS parameter is the subset of thefirst QoS parameters.

In one of the embodiments, the second QoS parameter includes at leastone of the following information: PQI, VQI, QFI, a data raterequirement, a communication range requirement, a correspondence betweenPQI, VQI, QFI, the data rate requirement, the communication rangerequirement and a radio bearer, PSID, and ITS-AID.

In one of the embodiments, the second QoS parameter includes at leastone of the following information: PQI, VQI, QFI, a data raterequirement, a communication range requirement, PSID, and ITS-AID.

In one of the embodiments, the method further includes sending, by thesecond terminal, second parameter information to the first terminal; andthe second parameter information includes a correspondence between PQI,VQI, QFI, a data rate requirement, a communication range requirement anda radio bearer.

In one of the embodiments, the second parameter information is carriedin the RRC signaling sent to the first terminal.

In one of the embodiments, the response message is carried in the RRCsignaling including the second parameter information.

In one of the embodiments, the connection between the first terminal andthe second terminal is a connection for at least one of the followinginformation: a QoS flow, PSID, ITS-AID, PQI, VQI, QFI, a data raterequirement, a communication range requirement, an application layer ID.

In one of the embodiments, the request message and/or the responsemessage includes a connection identification (ID), and the connection IDis used for distinguishing different connections between the firstterminal and the second terminal.

In one of the embodiments, at least one of the following informationcorresponding to the different connections between the first terminaland the second terminal is different: an IP address, an applicationlayer ID, PSID, ITS-AID, PQI, VQI, L2ID, a data rate requirement, acommunication range requirement.

In one of the embodiments, the request message includes an applicationlayer ID and/or L2ID used by the first terminal, and the applicationlayer ID used by the first terminal is different from an applicationlayer ID used by a current connection, and the L2ID used by the firstterminal is different from L2ID used by the current connection.

In one of the embodiments, the method further includes receiving, by thesecond terminal, a first connection update request message sent by thefirst terminal; and the first connection update request message includesan application layer ID and/or L2ID used by the first terminal, theapplication layer ID used by the first terminal is different from anapplication layer ID used by a current connection, and the L2ID used bythe first terminal is different from L2ID used by the currentconnection.

In one of the embodiments, the response message includes an applicationlayer ID and/or L2ID used by the second terminal, and the applicationlayer ID used by the second terminal is different from an applicationlayer ID used by a current connection, and the L2ID used by the secondterminal is different from L2ID used by the current connection.

In one of the embodiments, the method further includes sending, by thesecond terminal, a second connection update request message to the firstterminal; and the second connection update request message includes anapplication layer ID and/or L2ID used by the second terminal, and theapplication layer ID used by the second terminal is different from anapplication layer ID used by a current connection, and the L2ID used bythe second terminal is different from L2ID used by the currentconnection.

In one of the embodiments, request message for indicating to establish anew connection is sent by the first terminal in at least one of thefollowing situations: an IP address of an existing connection is notavailable for a new connection; an application layer ID of the existingconnection is not available for the new connection; PSID of the existingconnection is not available for the new connection; PQI of the existingconnection is not available for the new connection; VQI of the existingconnection is not available for the new connection; a data raterequirement of the existing connection is not available for the newconnection; a communication range requirement of the existing connectionis not available for the new connection; a radio bearer of the existingconnection is not available for the new connection; and L2ID of theexisting connection is not available for the new connection.

In one of the embodiments, the request message for indicating toestablish the new connection is carried in a PC5-S signaling or aPC5-RRC signaling.

In one of the embodiments, the new connection includes at least one ofthe following information: an IP address of the new connection isdifferent from an IP address of an existing connection; an applicationlayer ID of the new connection is different from an application layer IDof the existing connection; PSID of the new connection is different fromPSID of the existing connection; PQI, VQI, a data rate requirement, anda communication range requirement of the new connection are alldifferent from PQI, VQI, a data rate requirement, and a communicationrange requirement of the existing connection; a radio bearer of the newconnection is different from a radio bearer of the existing connection;and L2ID of the new connection is different from L2ID of the existingconnection.

In one of the embodiments, the method further includes any one of thefollowing information: the IP address of the existing connection is anIP address of the first terminal and/or the second terminal; the IPaddress of the existing connection is an IP address of the firstterminal and/or the second terminal in the existing connection; theapplication layer ID of the existing connection is an application layerID of the first terminal and/or the second terminal; the applicationlayer ID of the existing connection is an application layer ID of thefirst terminal and/or the second terminal in the existing connection;the L2ID of the existing connection is L2ID of the first terminal and/orthe second terminal; and the L2ID of the existing connection is L2ID ofthe first terminal and/or the second terminal in the existingconnection.

In one of the embodiments, before the second terminal sends the responsemessage to the first terminal, the method further includes receiving, bythe second terminal, configuration information sent by an access networkdevice; and the configuration information is used for indicating whetherto perform the connection operation between the first terminal and thesecond terminal for the second QoS parameter.

In one of the embodiments, after the second terminal sends the responsemessage to the first terminal, the method further includes receiving, bythe second terminal, configuration information sent by an access networkdevice; and the configuration information is used for indicating whetherto perform the connection operation between the first terminal and thesecond terminal for the second QoS parameter.

In one of the embodiments, the configuration information is specificallyused for indicating a physical layer parameter for the second QoSparameter.

In one of the embodiments, the configuration information is carried in asystem message or a RRC signaling sent to the second terminal.

In one of the embodiments, different types of core network devicescorrespond to different configuration information.

In one of the embodiments, before the second terminal receives theconfiguration information sent by the access network device, the methodfurther includes reporting, by the second terminal, a third QoSparameter to the access network device.

In one of the embodiments, the third QoS parameter includes at least oneof the following information: PQI, VQI, QFI, a data rate requirement, acommunication range requirement, a correspondence between PQI, VQI, QFI,the data rate requirement, the communication range requirement and aradio bearer, PSID, and ITS-AID.

In one of the embodiments, the correspondence includes a correspondenceused by the first terminal, which is sent by the first terminal.

In one of the embodiments, the correspondence includes a correspondencesent by the first terminal for configuring a correspondence used by thesecond terminal.

In one of the embodiments, third QoS parameters corresponding todifferent types of core network devices are different.

In one of the embodiments, the method further includes reporting, by thesecond terminal, a channel quality parameter of a connection from thefirst terminal to the second terminal to the access network device; andthe channel quality information includes at least one of a channel busyrate, RSRP, RSRQ, SINR, and RSSI.

In one of the embodiments, different channel quality parameterscorrespond to different configuration information.

In one of the embodiments, the configuration information is specificallyused for determining whether to perform the connection operation betweenthe first terminal and the second terminal for the second QoS parameteraccording to the channel quality information.

For the above-mentioned embodiments of the second terminal and variouspossible implementation manners, reference may be made to theembodiments of the first terminal, and details are not described hereinagain.

The following takes the scenario of FIG. 1 as an example, and FIGS. 5and 6 introduce the implementations of a single connection managementprocess and a dual connection management process, respectively. Thescheme is further explained by taking the establishing a connection,modifying a connection, and releasing a connection as examples.

FIG. 5 is a flowchart of a single connection management process providedby an embodiment of the present disclosure. In this embodiment, theentire process is divided into four parts, that is, connectionestablishment, connection modification (twice), and connection release.As shown in FIG. 5, establishing a connection may include the followingsteps.

In S501, UE1 reports QoS parameters related to UE1 and/or UE2 to gNB1.

In S502, gNB1 sends first configuration information to UE1.

In S503, UE1 sends a request message for establishing a connection toUE2.

In S504, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S505, gNB2 sends second configuration information to UE2.

In S506, UE2 sends a response message to UE1.

Optionally, in this embodiment, S501 and S502 may also be after S506,which is not limited in the present disclosure.

As shown in FIG. 5, the UE1 initiating the connection modification mayinclude the following steps.

In S511, UE1 reports QoS parameters related to UE1 and/or UE2 to gNB1.

In S512, gNB1 sends first configuration information to UE1.

In S513, UE1 sends a request message for modifying the connection toUE2.

In S514, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S515, gNB2 sends second configuration information to UE2.

In S516, UE2 sends a response message to UE1.

Optionally, in this embodiment, S511 and S512 may also be after S516,which is not limited in the present disclosure.

As shown in FIG. 5, the UE2 initiating the connection modification mayinclude the following steps.

In S521, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S522, gNB2 sends second configuration information to UE2.

In S523, UE2 sends a request message for modifying the connection toUE1.

In S524, UE1 reports QoS parameters related to UE1 and/or UE2 to gNB1.

In S525, gNB1 sends second configuration information to UE1.

In S526, UE1 sends a response message to UE2.

Optionally, in this embodiment, S521 and S522 may also be after S526,which is not limited in the present disclosure.

As shown in FIG. 5, UE2 initiating the connection release may includethe following steps.

In S531, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S532, gNB2 sends second configuration information to UE2.

In S533, UE2 sends a request message for releasing the connection toUE1.

In S534, UE1 sends a response message to UE2.

Optionally, in this embodiment, S531 and S532 may also be after S534,which is not limited in the present disclosure.

In this embodiment, for the QoS parameters, the configurationinformation, the response message, etc., reference may be made to thedescription of the foregoing embodiments, which will not be repeatedhere. In addition, the steps in this embodiment are not necessarilyperformed in sequence in the order indicated by the arrow. For example,the steps of UE reporting the QoS parameters to the base station and thebase station sending the configuration information to UE are notnecessarily executed every time. FIG. 5 is only a possibleimplementation, and the present disclosure is not limited to this.

FIG. 6 is a flowchart of a dual connection management process providedby an embodiment of the present disclosure. In this embodiment, theentire process is divided into three parts, that is, connectionestablishment (twice) and connection release. It should be noted thatunlike the embodiment in FIG. 5, the embodiment in FIG. 6 also includesa process of establishing a new connection, and FIG. 6 may also includea process of modifying the connection, and the present disclosure is notlimited to this. As shown in FIG. 6, establishing a connection mayinclude the following steps.

In S601, UE1 reports QoS parameters related to UE1 and/or UE2 to gNB1.

In S602, gNB1 sends first configuration information to UE1.

In S603, UE1 sends a request message for establishing a connection toUE2.

In S604, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S605, gNB sends second configuration information to UE2.

In S606, UE2 sends a response message to UE1.

Optionally, in this embodiment, S601 and S602 may also be after S606,which is not limited in the present disclosure.

As shown in FIG. 6, UE2 initiating the establishment of the newconnection may include the following steps.

In S611, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S612, gNB2 sends second configuration information to UE2.

In S613, UE2 sends a request message for establishing a new connectionto UE1.

In S614, UE1 reports QoS parameters related to UE1 and/or UE2 to gNB1.

In S615, gNB1 sends second configuration information to UE1.

In S616, UE1 sends a response message to UE2.

Optionally, in this embodiment, S611 and S612 may also be after S616,which is not limited in the present disclosure.

As shown in FIG. 6, UE2 initiating the connection release may includethe following steps.

In S621, UE2 reports QoS parameters related to UE2 and/or UE1 to gNB2.

In S622, gNB2 sends second configuration information to UE2.

In S623, UE2 sends a request message for releasing the connection to theUE1.

In S624, UE1 sends a response message to UE2.

Optionally, in this embodiment, S621 and S622 may also be after S624,which is not limited in the present disclosure.

In this embodiment, for the QoS parameters, the configurationinformation, the response message, etc., reference may be made to thedescription of the foregoing embodiments, which will not be repeatedhere. In addition, the steps in this embodiment are not necessarilyperformed in sequence in the order indicated by the arrow. For example,the steps of UE reporting the QoS parameters to the base station and thebase station sending the configuration information to UE are notnecessarily executed every time. FIG. 6 is only a possibleimplementation, and the present disclosure is not limited to this.

It should be understood, although blocks in the flowcharts of FIGS. 2-6are illustrated in sequence as indicated by arrows, the blocks are notnecessarily performed in sequence as indicated by the arrows. Unlessotherwise specifically specified in the specification, the execution ofthe blocks is not strictly limited, and the blocks may be performed inother sequences. Moreover, at least some of the blocks in FIGS. 2-6 mayinclude several sub-blocks or stages, which are not necessarilyperformed simultaneously, but may be executed at different times. Theexecution sequence of these sub-blocks or stages is not necessarilyperformed sequentially, but may be performed alternately with at least aportion of other blocks, or sub-blocks or stages of other blocks.

FIG. 7 is a block diagram of a connection management apparatus providedby an embodiment of the present disclosure. As shown in FIG. 7, theapparatus includes a processing module 11 and a sending module 12; theprocessing module 11 is configured to send a request message carrying afirst QoS parameter to a second terminal through the sending module 12;and the request message is used for indicating to perform a connectionoperation between a first terminal and the second terminal for the firstQoS parameter.

In one of the embodiments, as shown in FIG. 8, the apparatus furtherincludes a receiving module 13, configured to receive a response messagesent by the second terminal; and the response message is used forindicating whether the connection operation is successful.

FIG. 9 is a block diagram of a connection management apparatus providedby an embodiment of the present disclosure. As shown in FIG. 9, theapparatus includes a processing module 21 and a receiving module 22; theprocessing module 21 is configured to receive a request message carryinga first QoS parameter sent by a first terminal through the receivingmodule 22; and the request message is used for indicating to perform aconnection operation between the first terminal and a second terminalfor the first QoS parameter.

In one of the embodiments, as shown in FIG. 10, the apparatus furtherincludes a sending module 23, configured to send a response message tothe first terminal; and the response message is used for indicatingwhether the connection operation is successful.

For specific definitions of the connection management apparatus,reference may be made to the above definition of the connectionmanagement method, which will not be elaborated here. Respective modulesof the above-described connection management device may be implementedin whole or in part by software, hardware, and the combination thereof.Each of the above modules may be embedded in or independent of theprocessor in the computer device, or may be stored in a memory in thecomputer device in a software form, so that the processor invokes themto execute the operations corresponding to the above modules.

The embodiments of the present disclosure also provide a computerdevice, including a memory and a processor, the memory storing acomputer program, and the processor implements steps of the methoddescribed in any of the foregoing embodiments when executing thecomputer program.

The embodiments of the present disclosure also provide acomputer-readable storage medium having a computer program storedthereon, and the computer program, when executed by a processor,implements steps of the method described in any of the aboveembodiments.

In an embodiment, there is provided a computer device. The computerdevice may be a server, and its internal structure diagram may be asshown in FIG. 11. The computer device includes a processor, a memory, anetwork interface, and a database connected through a system bus. Theprocessor of the computer device is configured to provide calculationand control capabilities. The memory of the computer device includes anon-volatile storage medium and an internal memory. The non-volatilestorage medium stores an operating system, a computer program, and adatabase. The internal memory provides an environment for running theoperating system and the computer program in the non-volatile storagemedium. The database of the computer equipment is configured to storedata such as the QoS parameter and the configuration information. Thenetwork interface of the computer device is configured to communicatewith an external terminal through a network connection. The computerprogram is executed by the processor to realize the connectionmanagement method.

Those skilled in the art may understand that the structure shown in FIG.11 is only a block diagram of a part of the structure related to thesolution of the present disclosure, and does not constitute a limitationon the computer device to which the solution of the present disclosureis applied. A specific computer device may include more or less partsthan shown in the figure, or combine some parts, or have a differentpart arrangement.

Those ordinary skilled in the art may understand that all or part of theprocesses in the method of the foregoing embodiments may be implementedby instructing relevant hardware by a computer program. The computerprogram may be stored in a non-volatile computer readable storagemedium. When the computer program is executed, procedures of theabove-mentioned method embodiments may be included. Any reference to thememory, the storage, the database, or other media used in theembodiments provided by the present disclosure may include anon-volatile and/or a volatile memory. The suitable non-volatile memorymay include a read-only memory (ROM), a programmable ROM (PROM), anelectrically programmable ROM (EPROM), an electrically erasableprogrammable ROM (EEPROM), or a flash memory. The volatile memory mayinclude a random access memory (RAM) or an external cache memory. By wayof illustration, rather than limitation, the RAM is available in avariety of forms such as a static RAM (SRAM), a dynamic RAM (DRAM), asynchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), anenhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), a Rambus direct RAM(RDRAM), a direct Rambus dynamic RAM (DRDRAM), and a Rambus dynamic RAM(RDRAM).

The technical features of the above-mentioned implementations may becombined in any combination. For brevity of description, not allpossible combinations of the technical features in the aboveimplementations are described. However, as long as there is nocontradiction in combination of these technical features, it should beconsidered as the scope of the present specification. Theimplementations described above only provide several implementations ofthe present disclosure, and their descriptions are relatively specificand detailed, but they are not to be construed as limiting theprotection scope of the present disclosure. It should be noted that forthose of ordinary skill in the art, variations and improvements may bemade without departing from the concept of the present disclosure, whichfall within the protection scope of the present disclosure. Theprotection scope of the present disclosure is defined by the appendedclaims.

What is claimed is:
 1. A method for connection management, comprising:sending, by a first terminal, a request message carrying a first QoSparameter to a second terminal, wherein the request message is used forindicating to perform a connection operation between the first terminaland the second terminal according to the first QoS parameter, whereinthe connection between the first terminal and the second terminalcomprises connection for QoS flow, and the connection operationcomprises at least one of the following: establishing a connectionbetween the first terminal and the second terminal, modifying theconnection between the first terminal and the second terminal, orreleasing the connection between the first terminal and the secondterminal, wherein the request message for indicating to establish a newconnection is sent by the first terminal in the following situation: anapplication layer ID of an existing connection is not available for thenew connection, and wherein the request message for indicating toestablish the new connection is carried in a PC5-S signaling or aPC5-RRC signaling.
 2. The method according to claim 1, wherein themethod further comprises: receiving, by the first terminal, a responsemessage sent by the second terminal, wherein the response message isused for indicating whether the connection operation is successful. 3.The method according to claim 1, wherein the connection operationcomprises the establishing the connection between the first terminal andthe second terminal, and the request message comprises the first QoSparameter corresponding to the connection between the first terminal andthe second terminal to be established.
 4. The method according to claim1, wherein the connection operation comprises the modifying theconnection between the first terminal and the second terminal, and therequest message comprises the first QoS parameter corresponding to theconnection between the first terminal and the second terminal to bemodified.
 5. The method according to claim 1, wherein the connectionoperation comprises the releasing the connection between the firstterminal and the second terminal, and the request message comprises thefirst QoS parameter corresponding to the connection between the firstterminal and the second terminal to be released.
 6. The method accordingto claim 1, wherein the first QoS parameter comprises at least one ofthe following information: PQI, QFI, a data rate requirement, PSID, andITS-AID.
 7. The method according to claim 2, wherein the responsemessage comprises a second QoS parameter.
 8. The method according toclaim 7, wherein the second QoS parameter is a QoS parameter acceptableto the second terminal.
 9. The method according to claim 7, wherein thesecond QoS parameter comprises at least one of the followinginformation: PQI, QFI, a data rate requirement, PSID, and ITS-AID. 10.The method according to claim 1, wherein the method further comprisesany one of the following information: the IP address of the existingconnection is an IP address of at least one of the first terminal or thesecond terminal; the IP address of the existing connection is an IPaddress of at least one of the first terminal or the second terminal inthe existing connection; the application layer ID of the existingconnection is an application layer ID of at least one of the firstterminal or the second terminal; the application layer ID of theexisting connection is an application layer ID of at least one of thefirst terminal or the second terminal in the existing connection; theL2ID of the existing connection is L2ID of at least one of the firstterminal or the second terminal; and the L2ID of the existing connectionis L2ID of at least one of the first terminal or the second terminal inthe existing connection.
 11. A method for connection management,comprising: receiving, by a second terminal, a request message carryinga first QoS parameter sent by a first terminal, wherein the requestmessage is used for indicating to perform a connection operation betweenthe first terminal and the second terminal according to the first QoSparameter, wherein the connection between the first terminal and thesecond terminal comprises connection for QoS flow, and the connectionoperation comprises at least one of the following: establishing aconnection between the first terminal and the second terminal, modifyingthe connection between the first terminal and the second terminal, orreleasing the connection between the first terminal and the secondterminal, wherein the request message for indicating to establish a newconnection is received by the second terminal in the followingsituation: an application layer ID of an existing connection is notavailable for the new connection, and wherein the request message forindicating to establish the new connection is carried in a PC5-Ssignaling or a PC5-RRC signaling.
 12. A computer device comprising amemory and a processor, the memory storing a computer program, whereinthe processor is configured to execute the computer program to perform aconnection management method, comprising: sending, by a first terminal,a request message carrying a first QoS parameter to a second terminal,wherein the request message is used for indicating to perform aconnection operation between the first terminal and the second terminalaccording to the first QoS parameter, wherein the connection between thefirst terminal and the second terminal comprises connection for QoSflow, and the connection operation comprises at least one of thefollowing: establishing a connection between the first terminal and thesecond terminal, modifying the connection between the first terminal andthe second terminal, or releasing the connection between the firstterminal and the second terminal, wherein the request message forindicating to establish a new connection is sent by the first terminalin the following situation: an application layer ID of an existingconnection is not available for the new connection, and wherein therequest message for indicating to establish the new connection iscarried in a PC5-S signaling or a PC5-RRC signaling.
 13. The computerdevice according to claim 12, wherein the processor is furtherconfigured to perform: receiving, by the first terminal, a responsemessage sent by the second terminal, wherein the response message isused for indicating whether the connection operation is successful. 14.The computer device according to claim 12, wherein the connectionoperation comprises the establishing the connection between the firstterminal and the second terminal, and the request message comprises thefirst QoS parameter corresponding to the connection between the firstterminal and the second terminal to be established.
 15. The computerdevice according to claim 12, wherein the connection operation comprisesthe modifying the connection between the first terminal and the secondterminal, and the request message comprises the first QoS parametercorresponding to the connection between the first terminal and thesecond terminal to be modified.
 16. The computer device according toclaim 12, wherein the connection operation comprises the releasing theconnection between the first terminal and the second terminal, and therequest message comprises the first QoS parameter corresponding to theconnection between the first terminal and the second terminal to bereleased.
 17. The computer device according to claim 12, wherein thefirst QoS parameter comprises at least one of the following information:PQI, QFI, a data rate requirement, PSID, and ITS-AID.
 18. A computerdevice comprising a memory and a processor, the memory storing acomputer program, wherein the processor is configured to execute thecomputer program to perform a connection management method, comprising:receiving, by a second terminal, a request message carrying a first QoSparameter sent by a first terminal, wherein the request message is usedfor indicating to perform a connection operation between the firstterminal and the second terminal according to the first QoS parameter,wherein the connection between the first terminal and the secondterminal comprises connection for QoS flow, and the connection operationcomprises at least one of the following: establishing a connectionbetween the first terminal and the second terminal, modifying theconnection between the first terminal and the second terminal, orreleasing the connection between the first terminal and the secondterminal, wherein the request message for indicating to establish a newconnection is received by the second terminal in the followingsituation: an application layer ID of an existing connection is notavailable for the new connection, and wherein the request message forindicating to establish the new connection is carried in a PC5-Ssignaling or a PC5-RRC signaling.